Home > SW > BDII core
BDII core - 1.1.0
Current State :: Production
Contact :: cristina.aiftimiei@pd.infn.it
Technical Contact :: cristina.aiftimiei@pd.infn.it
Description :: The resource-level BDII is an instance of the BDII that contains information about a Grid Service and is typically deployed with the service itself. It consists of an OpenLDAP database that is periodically updated by a parallel process that obtains information about the Grid Service from one or more information sources.
Release Date :: 20110901
Major Version :: 1
Minor Version :: 1
Revision Version :: 0
Release Notes ::
What's new:
This release of BDII core addresses a number of minor issues reported with the initial EMI 1 release. Most of the issues fixed are related to packaging and the templates provided by the glite-info-provider-service component.
One new useful feature has been included which is an improved status command which detects that the BDII is not updating. The yaim configuration has also been improved so that the BDII will automatically start on reboot. Improve status command to detect hanging BDII.
Version 1.7.0 of glite-info-provider-service has the following updates in addtion:
* There is a completely new GLUE 2 provider for VOMS. This should be called like:
o glite-info-glue2-voms glite-info-glue2-voms.conf[,glite-info-glue2-voms-admin.conf]
where the voms-admin config file should only be included if voms-admin is running on the server. The relevant config templates are glite-info-glue2-voms.conf.template and glite-info-glue2-voms-admin.conf.template, and it should normally be possible to use them without modification. This provider creates a single GLUE2Service object with one GLUE2Endpoint per VO for each of voms and voms-admin.
* For the WMS (wmproxy) the DN is now extracted using openssl rather than grid-cert-info, but there should be no effect on the published information. Also the GLUE 2 publisher will have GLUE2EndpointServingState: draining if a file /etc/glite-wms/.drain exists.
* The GLUE 2 information for the RTEPublisher (software tag publisher) has been revamped to fit within the ComputingService structure in CREAM. In particular the service type (EndpointInterfaceName) is now org.glite.ce.ApplicationPublisher.
* There is a new GLUE 2 template for the CEMon, again intended to fit within the ComputingService structure for CREAM.
* The VOMS, WMS (wmproxy) and CEMon templates and scripts have been updated to reflect the new paths, environment variables, RPM names and documentation locations in EMI, and hence are no longer compatible with gLite installations.
* A bug in the GLUE 2 publisher has been fixed that prevented the publication of multiple Extension objects with the same Key.
* The old beta-test GLUE 2 publisher has been renamed and replaced by a script which calls the new publisher, so any service which is still configured to use it will publish in the more up-to-date format.
* The wrapper around the service status query has been extended to allow extra arguments to be passed to the init.d script. This is used by voms and should otherwise be transparent.
This release also include the BDII Nagios probe. This probe is already running in production but has been repackaged for release within EMI.
Additional Details :: https://wiki.egi.eu/wiki/UMD-1:UMD-1.3.0#emi.bdii-core.sl5.x86_64
Change LOG ::
Put the Change logs here (multiline field)
Repository URL :: sw/production/umd/1/sl5/x86_64/updates
Documentation Links ::
Keywords ::